Collection of Internet/Collection of Internet.iso/infosrvr/doc/www_talk.arc/[e-mail] _Fri Dec 6 01:33:36 1991.msg

Internet Message Format | 1992-11-30 | 2KB

Return-Path: <[e-mail]>
Received: from dxmint.cern.ch by  nxoc01.cern.ch  (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
    id AA04159; Fri, 6 Dec 91 01:33:36 GMT+0100
Received: by dxmint.cern.ch (cernvax) (5.57/3.14)
    id AA20299; Fri, 6 Dec 91 01:22:17 +0100
Received: by shelley.aa.ox.com (/\==/\ Smail3.1.22.1 #22.9)
    id <[e-mail]>; Thu, 5 Dec 91 19:14 EST
Message-Id: <[e-mail]>
To: [e-mail]
Cc: [e-mail], [e-mail], [e-mail]
Subject: Re: documents, files, types, and access methods
In-Reply-To: Your message of Thu, 05 Dec 91 12:16:11 -0600.
             <[e-mail]>
Date: Thu, 05 Dec 91 19:14:37 -0500
From: Edward Vielmetti <[e-mail]>
X-Mts: smtp

data, data, data, data, data.

if you have good ideas about document structure and ways to send
messages around that have magic cookies in them, that's good.  but in
order to convince anyone to do anything substantial in terms of
software development you need to provide data.

get 100 entries describing 100 things that are useful, add enough
structure that a motivated party can pull your database apart and
create something new from it, and people will start to write code.
(honest.)  produce another 10 entries a month for a year and more
people will write code or bend their existing code to work with your
system.

Don't wait for an all-singing, all-dancing standard before you start
to collect information.  If you gather enough stuff and organize it
well, other people will do the work of bringing it up to what is
considered standard (if and when that happens).  You do need to be
thorough in making sure that whatever you do is consistent and regular
enough to be worth retrofitting.

--
Edward Vielmetti, vice president for research, MSEN Inc. [e-mail]
       MSEN, Inc. 628 Brooks Ann Arbor MI 48103 [phone]